-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
util: improve inspect performance #20009
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nodejs-github-bot
added
the
util
Issues and PRs related to the built-in util module.
label
Apr 13, 2018
BridgeAR
added
the
performance
Issues and PRs related to the performance of Node.js.
label
Apr 13, 2018
Can you post the benchmark results? |
@jasnell I posted them in the description below the code? |
oh, missed that. Is there not an existing benchmark script that works with compare.js? Seeing those results would be more reliable I think. |
Just a few runs:
|
jasnell
approved these changes
Apr 13, 2018
BridgeAR
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Apr 13, 2018
addaleax
approved these changes
Apr 13, 2018
hiroppy
approved these changes
Apr 14, 2018
trivikr
approved these changes
Apr 14, 2018
This improves a slow code part in `util.inspect` by directly retrieving the `Symbol.toStringTag` and by optimizing some code paths.
BridgeAR
force-pushed
the
improve-util-inspect-performance
branch
from
April 16, 2018 15:39
6f1355b
to
de7e7e7
Compare
Rebased New CI https://ci.nodejs.org/job/node-test-pull-request/14332/ |
CI failed. PTAL |
Landed in ad1d105 |
BridgeAR
added a commit
to BridgeAR/node
that referenced
this pull request
Apr 19, 2018
This improves a slow code part in `util.inspect` by directly retrieving the `Symbol.toStringTag` and by optimizing some code paths. PR-URL: nodejs#20009 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
jasnell
pushed a commit
that referenced
this pull request
Apr 20, 2018
This improves a slow code part in `util.inspect` by directly retrieving the `Symbol.toStringTag` and by optimizing some code paths. PR-URL: #20009 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
performance
Issues and PRs related to the performance of Node.js.
util
Issues and PRs related to the built-in util module.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This improves a slow code part in
util.inspect
by directlyretrieving the
Symbol.toStringTag
and by optimizing some codepaths.
I benchmarked this with #20007 applied.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes